`GET /api/v1/orders/{orderId}/funding` — fetch the StableFX funding `typedData` to sign.

Recovery path: the order-create response normally carries the funding action in its nextActions, but if the create-time presign prefetch failed the client can fetch the typed data here on demand (it is re-derived server-side from the order’s contractTradeId). Returns the signTypedData action (typed data + where to submit the signature) or 404 when the order has no pending funding step.

GET /api/v1/orders/{orderId}/funding

`GET /api/v1/orders/{orderId}/funding` — fetch the StableFX funding `typedData` to sign.

cURL

curl --request GET \
  --url https://api.tetrafi.io/api/v1/orders/{orderId}/funding \
  --header 'X-API-Key: <api-key>'

400

{
  "docUrl": "<string>",
  "error": "<string>",
  "message": "<string>",
  "retryable": true,
  "timestamp": 123,
  "details": {
    "capabilityBlockers": [
      {
        "code": "WORKSPACE_NOT_FOUND",
        "estimate": "minutes",
        "message": "<string>",
        "unlockStep": "finish_onboarding",
        "currentlyDue": [
          "<string>"
        ]
      }
    ],
    "conflicts": [
      "<string>"
    ],
    "field": "<string>",
    "reason": "<string>",
    "remediation": "<string>",
    "retryAfter": "PT120S",
    "value": "<string>"
  },
  "next": {
    "kind": "order"
  },
  "requestId": "<string>"
}

Authorizations

api_keybearer_auth

X-API-Key · string · header · required

Send the API key in X-API-Key.

Request signing. A key with signing enabled (POST /api/v1/workspaces/{workspaceId}/users/me/api-keys/{keyId}/signing, which returns the signing secret once) must also sign every request:

• X-Timestamp: the current Unix time in seconds, within 300 seconds of the server clock.
• X-Signature: lower-case hex HMAC-SHA256 of the canonical string, keyed with the signing secret's 32 bytes (the secret is 64 hex characters; decode it first).

The canonical string is four lines joined by \n, with no trailing newline: the X-Timestamp value, the upper-case method, the path with its query exactly as sent (/api/v1/orders?limit=1), and the lower-case hex SHA-256 of the exact body bytes (the SHA-256 of an empty body when there is none).

A write's signature (POST, PUT, PATCH, DELETE) is accepted once: sending the same signed write again is refused, so a retry signs again. A read (GET, HEAD) changes nothing, so an identical signed read inside the window is admitted again and polling needs no nonce.

A signing refusal is a 401 AUTH_REQUIRED whose details.reason names the cause: SIGNATURE_REQUIRED (a header is missing), SIGNATURE_INVALID (a malformed header or a wrong signature), TIMESTAMP_OUT_OF_RANGE or SIGNATURE_REPLAYED.

Headers

X-Workspace-Id · string<uuid>

The workspace the request acts in. An API key bound to a workspace implies it: omit the header, or send that same id (another id answers 403 WORKSPACE_SCOPE_MISMATCH). A member session must send it (400 MISSING_WORKSPACE without it).

Path Parameters

orderId · string · required

Order ID

Response

200

Funding typed data to sign